Integrate upstream changes from develop#92
Integrate upstream changes from develop#92carole-lavillonniere wants to merge 11 commits intolocalstackfrom
Conversation
* chore(deps): Update go-chi to v5.2.2
* Add support for multi-tenancy --------- Co-authored-by: Chengjun Li <>
* ci: scope down permissions for release.yml * ci: scope down permissions for integ-tests.yml * ci: scope down permissions for check-binaries.yml
* Update from upstream - 2026-03-18 * Update from upstream - 2026-03-18 * Update from upstream - 2026-03-18 * Update from upstream - 2026-03-19 * Update from upstream - 2026-03-19 * Potential fix for code scanning alert no. 7: Workflow does not contain permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> * Update from upstream - 2026-03-27 * Update from upstream - 2026-03-30 --------- Co-authored-by: lambda-tooling+rie <lambda-tooling+rie@amazon.com> Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
* Update from upstream - 2026-03-18 * Update from upstream - 2026-03-18 * Update from upstream - 2026-03-18 * Update from upstream - 2026-03-19 * Update from upstream - 2026-03-19 * Potential fix for code scanning alert no. 7: Workflow does not contain permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> * Update from upstream - 2026-03-27 * Update from upstream - 2026-03-30 * Update from upstream - 2026-04-01 --------- Co-authored-by: lambda-tooling+rie <lambda-tooling+rie@amazon.com> Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
…-changes-from-2026-02-12
joe4dev
left a comment
There was a problem hiding this comment.
These upstream changes were already reviewed, so we assume they are fine as long as they pass the full LocalStack test suite (including localstack-pro).
Resolves all merge conflicts preserving LocalStack customizations while integrating upstream additions
What merge conflicts were these?
Wouldn't we expect no more merge conflicts given the two one-line fixes merged in aws#176 ?
| package invoke | ||
|
|
||
| const ( | ||
| RequestIdHeader = "X-Amzn-RequestId" |
There was a problem hiding this comment.
FYI: Interesting to see RequestId supported natively via headers now, which differs from our current approach sending it via the LS invoke payload.
| const ( | ||
| RequestIdHeader = "X-Amzn-RequestId" | ||
|
|
||
| ClientContextHeader = "X-Amz-Client-Context" |
|
Closing this PR, given the changes are already merged manually and released as v0.1.44-pre, following our guidance https://github.com/localstack/lambda-runtime-init/blob/localstack/README-LOCALSTACK.md#integrate-upstream-changes |
developintolocalstackbranch following this guide